|
Services
2017/04/13 |
| [1] | It's possible to make sure services' status like follows. |
|
# display the list of services which are running root@dlp:~# systemctl -t service UNIT LOAD ACTIVE SUB DESCRIPTION accounts-daemon.service loaded active running Accounts Service apparmor.service loaded active exited LSB: AppArmor initialization console-setup.service loaded active exited Set console keymap cron.service loaded active running Regular background program pr dbus.service loaded active running D-Bus System Message Bus ... ... ... ufw.service loaded active exited Uncomplicated firewall user@0.service loaded active running User Manager for UID 0 LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 35 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. # the list of all services' setting root@dlp:~# systemctl list-unit-files -t service UNIT FILE STATE accounts-daemon.service enabled apparmor.service enabled apt-daily.service static autovt@.service enabled ... ... ... user@.service static uuidd.service indirect x11-common.service masked 144 unit files listed. |
| [2] | Stop and turn OFF auto-start setting for a service if you don'd need it. (it's Apparmor as an example below) |
|
root@dlp:~# systemctl stop apparmor root@dlp:~# systemctl disable apparmor |